SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Service-oriented modeling</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Service-oriented modeling</span></span>

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .ambox{border:1px solid #a2a9b1;border-left:10px solid #36c;background-color:#fbfbfb;box-sizing:border-box}.mw-parser-output .ambox+link+.ambox,.mw-parser-output .ambox+link+style+.ambox,.mw-parser-output .ambox+link+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+style+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+link+.ambox{margin-top:-1px}html body.mediawiki .mw-parser-output .ambox.mbox-small-left{margin:4px 1em 4px 0;overflow:hidden;width:238px;border-collapse:collapse;font-size:88%;line-height:1.25em}.mw-parser-output .ambox-speedy{border-left:10px solid #b32424;background-color:#fee7e6}.mw-parser-output .ambox-delete{border-left:10px solid #b32424}.mw-parser-output .ambox-content{border-left:10px solid #f28500}.mw-parser-output .ambox-style{border-left:10px solid #fc3}.mw-parser-output .ambox-move{border-left:10px solid #9932cc}.mw-parser-output .ambox-protection{border-left:10px solid #a2a9b1}.mw-parser-output .ambox .mbox-text{border:none;padding:0.25em 0.5em;width:100%}.mw-parser-output .ambox .mbox-image{border:none;padding:2px 0 2px 0.5em;text-align:center}.mw-parser-output .ambox .mbox-imageright{border:none;padding:2px 0.5em 2px 0;text-align:center}.mw-parser-output .ambox .mbox-empty-cell{border:none;padding:0;width:1px}.mw-parser-output .ambox .mbox-image-div{width:52px}@media(min-width:720px){.mw-parser-output .ambox{margin:0 10%}}@media print{body.ns-0 .mw-parser-output .ambox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1248332772">

/* start https://en.wikipedia.org/ */

.mw-parser-output .multiple-issues-text{width:95%;margin:0.2em 0}.mw-parser-output .multiple-issues-text>.mw-collapsible-content{margin-top:0.3em}.mw-parser-output .compact-ambox .ambox{border:none;border-collapse:collapse;background-color:transparent;margin:0 0 0 1.6em!important;padding:0!important;width:auto;display:block}body.mediawiki .mw-parser-output .compact-ambox .ambox.mbox-small-left{font-size:100%;width:auto;margin:0}.mw-parser-output .compact-ambox .ambox .mbox-text{padding:0!important;margin:0!important}.mw-parser-output .compact-ambox .ambox .mbox-text-span{display:list-item;line-height:1.5em;list-style-type:disc}body.skin-minerva .mw-parser-output .multiple-issues-text>.mw-collapsible-toggle,.mw-parser-output .compact-ambox .ambox .mbox-image,.mw-parser-output .compact-ambox .ambox .mbox-imageright,.mw-parser-output .compact-ambox .ambox .mbox-empty-cell,.mw-parser-output .compact-ambox .hide-when-compact{display:none}

/* end https://en.wikipedia.org/ */

</style>

<p><b>Service-oriented modeling</b> is the discipline of modeling business and software systems, for the purpose of designing and specifying <a href="Service-orientation" title="Service-orientation">service-oriented</a> business systems within a variety of architectural styles and paradigms, such as <a href="Application_architecture" class="mw-redirect" title="Application architecture">application architecture</a>, <a href="Service-oriented_architecture" title="Service-oriented architecture">service-oriented architecture</a>, <a href="Microservice" class="mw-redirect" title="Microservice">microservices</a>, and <a href="Cloud_computing" title="Cloud computing">cloud computing</a>.

</p><p>Any service-oriented modeling method typically includes a <a href="Modeling_language" title="Modeling language">modeling language</a> that can be employed by both the "problem domain organization" (the business), and "solution domain organization" (the <a href="Information_technology" title="Information technology">information technology</a> department), whose unique perspectives typically influence the <a href="Service_(systems_architecture)" title="Service (systems architecture)">service</a> development life-cycle strategy and the projects implemented using that strategy.

</p><p>Service-oriented modeling typically strives to create models that provide a comprehensive view of the analysis, design, and architecture of all software entities in an organization, which can be understood by individuals with diverse levels of business and technical understanding. Service-oriented modeling typically encourages viewing software entities as "assets" (service-oriented assets), and refers to these assets collectively as "services." A key service design concern is to find the right <a href="Service_granularity_principle" title="Service granularity principle">service granularity</a> both on the business (domain) level and on a technical (interface contract) level.

</p>

<div class="mw-heading mw-heading2"><h2 id="Popular_approaches">Popular approaches</h2></div>

<p>Several approaches have been proposed specifically for designing and modeling services, including SDDM, SOMA and SOMF.

</p>

<div class="mw-heading mw-heading3"><h3 id="Service-oriented_design_and_development_methodology">Service-oriented design and development methodology</h3></div>

<p>Service-oriented design and development methodology (SDDM) is a fusion method created and compiled by M. Papazoglou and W.J. van den Heuvel.<sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> The paper argues that SOA designers and service developers cannot be expected to oversee a complex service-oriented development project without relying on a sound design and development methodology. It provides an overview of the methods and techniques used in service-oriented design, approaches the service development methodology from the point of view of both service producers and requesters, and reviews the range of SDDM elements that are available to these roles.

</p><p>An update to SDDM was later published in <i>Web Services and SOA: Principles and Technology</i> by M. Papazoglou.<sup id="cite_ref-2" class="reference"><a href="#cite_note-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading3"><h3 id="Service-oriented_modeling_and_architecture">Service-oriented modeling and architecture</h3></div>

<p><a href="IBM" title="IBM">IBM</a> announced service-oriented modeling and architecture (SOMA) as its SOA-related methodology in 2004 and published parts of it subsequently.<sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup> SOMA refers to the more general domain of service modeling necessary to design and create SOA. SOMA covers a broader scope and implements service-oriented analysis and design (SOAD) through the identification, specification and realization of services, components that realize those services (a.k.a. "service components"), and flows that can be used to compose services.

</p><p>SOMA includes an analysis and design method that extends traditional object-oriented and component-based analysis and design methods to include concerns relevant to and supporting SOA. It consists of three major phases of identification, specification and realization of the three main elements of SOA, namely, services, components that realize those services (aka service components) and flows that can be used to compose services.

</p><p>SOMA is an end-to-end SOA method for the identification, specification, realization and implementation of services (including information services), components, flows (processes/composition). SOMA builds on current techniques in areas such as domain analysis, functional areas grouping, variability-oriented analysis (VOA) process modeling, component-based development, object-oriented analysis and design and use case modeling. SOMA introduces new techniques such as goal-service modeling, service model creation and a service litmus test to help determine the granularity of a service.

</p><p>SOMA identifies services, component boundaries, flows, compositions, and information through complementary techniques which include domain decomposition, goal-service modeling and existing asset analysis.

The service lifecycle in SOMA consists of the phases of identification, specification, realization, implementation, deployment and management in which the fundamental building blocks of SOA are identified then refined and implemented in each phase. The fundamental building blocks of SOA consist of services, components, flows and related to them, information, policy and contracts.<sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading3"><h3 id="Service-oriented_modeling_framework">Service-oriented modeling framework</h3></div>

<p>Service-oriented modeling framework (SOMF) has been devised by author <a href="Michael_B.T._Bell" class="mw-redirect" title="Michael B.T. Bell">Michael Bell</a> as a holistic and anthropomorphic modeling language for <a href="Software_development" title="Software development">software development</a> that employs disciplines and a universal language to provide tactical and strategic solutions to enterprise problems.<sup id="cite_ref-Bell_5-0" class="reference"><a href="#cite_note-Bell-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup> The term "holistic language" pertains to a modeling language that can be employed to design any application, business and technological environment, either local distributed, or federated. This universality may include design of application-level and enterprise-level solutions, including SOA landscapes, <a href="Cloud_computing" title="Cloud computing">cloud computing</a>, or <a href="Big_data" title="Big data">big data</a> environments. The term "anthropomorphic", on the other hand, affiliates the SOMF language with intuitiveness of implementation and simplicity of usage.

</p>

<div class="mw-heading mw-heading4"><h4 id="Discipline-specific_modeling_process">Discipline-specific modeling process</h4></div>

<p>SOMF is a service-oriented development life cycle methodology, a <a href="Discipline" title="Discipline">discipline-specific</a> modeling process. It offers a number of modeling practices and related disciplines that contribute to a successful service-oriented life cycle development and modeling during a project. The image below illustrates the major elements that identify the “what to do” aspects of a service development scheme. These are the modeling pillars that will enable practitioners to craft an effective project plan and to identify the milestones of a service-oriented initiative—either a small or large-scale business or a technological venture.<br>

</p>

<div class="mw-heading mw-heading4"><h4 id="SOMF_building_blocks">SOMF building blocks</h4></div>

<p>Furthermore, the video clip below, depicts the three SOMF building blocks, segments that drive the service-oriented modeling process:

</p>

<ol><li><b>Practices and Modeling Environments.</b> These are the two overlapping Abstraction and Realization Practices that are implemented in three service-oriented modeling environments: Conceptual Environment, Analysis Environment, and Logical Environment.</li>

<li><b>Modeling Disciplines.</b> Each service-oriented modeling environment is driven by a related discipline: Conceptual Architecture Discipline, Service Discovery & Analysis Discipline, and Logical Architecture Discipline.</li>

<li><b>Artifacts.</b> This SOMF segment identifies the chief artifacts required for each modeling environment.</li></ol>

/* start https://en.wikipedia.org/ */

.mw-parser-output .div-col{margin-top:0.3em;column-width:30em}.mw-parser-output .div-col-small{font-size:90%}.mw-parser-output .div-col-rules{column-rule:1px solid #aaa}.mw-parser-output .div-col dl,.mw-parser-output .div-col ol,.mw-parser-output .div-col ul{margin-top:0}.mw-parser-output .div-col li,.mw-parser-output .div-col dd{page-break-inside:avoid;break-inside:avoid-column}

/* end https://en.wikipedia.org/ */

</style><div class="div-col div-col-small" style="column-width: 20em;">

<ul><li><a href="Domain-driven_design" title="Domain-driven design">Domain-driven design</a></li>

<li><a href="Object-oriented_analysis_and_design" title="Object-oriented analysis and design">Object-oriented analysis and design</a></li>

<li><a href="Service-oriented_architecture" title="Service-oriented architecture">Service-oriented architecture</a></li>

<li><a href="Service_granularity_principle" title="Service granularity principle">Service granularity principle</a></li>

<li><a href="Unified_Modeling_Language" title="Unified Modeling Language">Unified Modeling Language</a></li>

<li><a href="Michael_B.T._Bell" class="mw-redirect" title="Michael B.T. Bell">Michael Bell's Methodologies</a></li></ul>

</div>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist reflist-columns references-column-width" style="column-width: 30em;">

<li id="cite_note-1"><span class="mw-cite-backlink"><b><a href="#cite_ref-1">^</a></b></span> <span class="reference-text">Mike P. Papazoglou, Willem-Jan van den Heuvel:

Service-oriented design and development methodology. Int. J. Web Eng. Technol. 2(4): 412–442 (2006)</span>

</li>

<li id="cite_note-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-2">^</a></b></span> <span class="reference-text">M. Papazoglou, INFOLAB, Tilburg University, The Netherlands (2013) <a rel="nofollow" class="external text" href="http://catalogue.pearsoned.ca/educator/product/Web-Services-and-SOA-Principles-and-Technology/9780273732167.page">Web Services and SOA: Principles and Technology (2nd Edition)</a>, Pearson Education Canada, Paper, 856 pp, published 01/13/2012, <style data-mw-deduplicate="TemplateStyles:r1238218222">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9780273732167</bdi></span>

</li>

<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3">^</a></b></span> <span class="reference-text">Ali Arsanjani, Abdul Allam:

Service-Oriented Modeling and Architecture for Realization of an SOA. IEEE SCC 2006: 521</span>

</li>

<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4">^</a></b></span> <span class="reference-text">Bieberstein et al., Executing SOA: A Practical Guide for the Service-Oriented Architect (Paperback), IBM Press books, 978-0132353748</span>

</li>

<li id="cite_note-Bell-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-Bell_5-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFBell2008" class="citation book cs1">Bell, Michael (2008). "Introduction to Service-Oriented Modeling". <span class="id-lock-registration" title="Free registration required"><a rel="nofollow" class="external text" href="https://archive.org/details/serviceorientedm0000bell"><i>Service-Oriented Modeling: Service Analysis, Design, and Architecture</i></a></span>. Wiley & Sons. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-470-14111-3</bdi>.</cite></span>

</li>

</ol></div>

<div class="mw-heading mw-heading2"><h2 id="Further_reading">Further reading</h2></div>

<ul><li>Ali Arsanjani et al. (2008). "<a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/search/freesrchabstract.jsp?tp=&arnumber=5386496&queryText%3DSOMA%26openedRefinements%3D*%26searchField%3DSearch+All">SOMA: A method for developing service-oriented solutions </a>". IBM systems Journal Oct 2008</li>

<li>Michael Bell (2008). <i>Service-Oriented Modeling: Service Analysis, Design, and Architecture</i>. Wiley.</li>

<li>Birol Berkem (2008). "<a rel="nofollow" class="external text" href="http://www.jot.fm/issues/issue_2008_11/column6.pdf">From The Business Motivation Model (BMM) To Service Oriented Architecture (SOA)</a>" In: <i>Journal of Object Technology</i> Vol 7, no. 8</li>

<li><a href="M._Brian_Blake" title="M. Brian Blake">M. Brian Blake</a> (2007). "<a rel="nofollow" class="external text" href="http://www.cs.georgetown.edu/~blakeb/pubs/blake_IEEESoftware2007_proof.pdf">Decomposing Composition: Service-Oriented Software Engineers</a>". In: <i>IEEE Software</i>. Nov/Dec 2007. pp. 68–77.</li>

<li>Michael P. Papazoglou, Web Services - Principles and Technology. Prentice Hall 2008, <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-321-15555-9</bdi></li>

<li>Dick A. Quartel, Maarten W. Steen, Stanislav Pokraev, Marten J. Sinderen, COSMO: A conceptual framework for service modelling and refinement, Information Systems Frontiers, v.9 n.2-3, p. 225–244, July 2007</li>

<li>Luba Cherbakov et al. (2006). "<a rel="nofollow" class="external text" href="http://www.ibm.com/developerworks/webservices/library/ws-soa-in-action/">SOA in action inside IBM, Part 1: SOA case studies</a>". IBM developerWorks</li></ul>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .side-box{margin:4px 0;box-sizing:border-box;border:1px solid #aaa;font-size:88%;line-height:1.25em;background-color:var(--background-color-interactive-subtle,#f8f9fa);display:flow-root}.mw-parser-output .infobox .side-box{font-size:100%}.mw-parser-output .side-box-abovebelow,.mw-parser-output .side-box-text{padding:0.25em 0.9em}.mw-parser-output .side-box-image{padding:2px 0 2px 0.9em;text-align:center}.mw-parser-output .side-box-imageright{padding:2px 0.9em 2px 0;text-align:center}@media(min-width:500px){.mw-parser-output .side-box-flex{display:flex;align-items:center}.mw-parser-output .side-box-text{flex:1;min-width:0}}@media(min-width:720px){.mw-parser-output .side-box{width:238px}.mw-parser-output .side-box-right{clear:right;float:right;margin-left:1em}.mw-parser-output .side-box-left{margin-right:1em}}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1237033735">

/* start https://en.wikipedia.org/ */

@media print{body.ns-0 .mw-parser-output .sistersitebox{display:none!important}}@media screen{html.skin-theme-clientpref-night .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}

/* end https://en.wikipedia.org/ */

</style><div class="side-box side-box-right sistersitebox"><style data-mw-deduplicate="TemplateStyles:r1126788409">

/* start https://en.wikipedia.org/ */

.mw-parser-output .plainlist ol,.mw-parser-output .plainlist ul{line-height:inherit;list-style:none;margin:0;padding:0}.mw-parser-output .plainlist ol li,.mw-parser-output .plainlist ul li{margin-bottom:0}

/* end https://en.wikipedia.org/ */

</style>

<div class="side-box-text plainlist">Wikimedia Commons has media related to <span style="font-weight: bold; font-style: italic;"><a href="https://commons.wikimedia.org/wiki/Category:Service-oriented_modeling" class="extiw external" title="commons:Category:Service-oriented modeling">Service-oriented modeling</a></span>.</div></div>

</div>

<ul><li><a rel="nofollow" class="external text" href="http://www.ibm.com/developerworks/library/ws-soad1/index.html">Elements of Service-Oriented Analysis and Design</a>, IBM developerWorks Web services zone, June 2004</li>

<li><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://pure.uvt.nl/ws/files/795806/papazogloump-2006-88.pdf">"Service-Oriented Design and Development Methodology"</a> <span class="cs1-format">(IJWET paper)</span>. Inderscience Enterprises Ltd.</cite></li>

<li><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.ibm.com/developerworks/library/ws-soa-design1/ws-soa-design1-pdf.pdf">"Service-oriented modeling and architecture: How to identify, specify, and realize services for your SOA"</a> <span class="cs1-format">(Softcopy)</span>. IBM Corporation.</cite></li>

<li><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20120417093034/http://www.modelingconcepts.com/pdf/SOMF_2.1_Conceptualization_Model_Language_Specifications.pdf">"SOMF 2.1 Service-Oriented Conceptualization Model Specifications"</a> <span class="cs1-format">(PDF)</span>. Methodologies Corporation. Archived from <a rel="nofollow" class="external text" href="http://www.modelingconcepts.com/pdf/SOMF_2.1_Conceptualization_Model_Language_Specifications.pdf">the original</a> <span class="cs1-format">(Softcopy)</span> on 2012-04-17<span class="reference-accessdate">. Retrieved <span class="nowrap">2011-02-08</span></span>.</cite></li>

<li><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.modelingconcepts.com/pages/download.htm">"SOMF Examples & Language Notation"</a> <span class="cs1-format">(Softcopy)</span>. Methodologies Corporation.</cite></li></ul></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2024-08-18" href="https://en.wikipedia.org/wiki/?title=Service-oriented_modeling&oldid=1240957236">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>